Keep sub-evaluators up to date after integration step #97
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Evaluators which contain "children" evaluators such as systems should be given the chance to keep their sub-evaluators up to date after events like an integrator step. With the
update()
method, an external source can notify the evaluator when its state has been updated so that it can then go and update its children.This is useful for callbacks, since callbacks will probably want to query individual components rather than systems.
Closes #96
Proposed changes
Add a new
update()
interface toEvaluator
which anyone who updates anEvaluator
's state manually (such as integrators) can let theEvaluator
know that its state has been modified. By default, anEvaluator
will choose to ignore this notice, butSystem
s can then update all of their children.Checklist
-Wall -Wpedantic -Wconversion -Wextra
.Further comments
Waiting on #91, which somewhat demonstrates more why we would want this change.